We distinguish two different roles here.

• This role typically specifies and maintains business requirements connected to processes and information. This type of role is a sub role of the Business Analyst role where he is responsible for capturing and maintaining business requirements.
• The second role is used in RUP projects or other  software development domain. For a more detailed description see the appropriate documentation from the software development domain. In this sense this role is responsible for specifying the detailed system requirements.

Different aspects of the requirements are typically documented in different types of requirements work products; as such the requirements will usually be defined in multiple work products. A person playing this role may be responsible for many of those work products.

A person acting in this role needs good communication skills, both in terms of expressing themselves verbally and in writing. Knowledge of the business and technology domain is also important, but is not typically necessary for every project team member acting in this role. For this role to be carried out efficiently, the person playing this role needs to be familiar with the productivity tools used to capture the results of the requirements work.